Systems and methods for the incremental and reversible deployment of a biometric identity management system

ABSTRACT

This disclosure describes methods and systems for a biometric identity management system capable of being deployed incrementally one organization at a time, and also reversibly, such that any organization can unsubscribe at any time. A biometric processing engine can perform biometric matching between records from a first database and a second database, whereby the databases have been established independently of each other. Each record comprises a biometric record and a corresponding identifier unique across databases. If a biometric record of a first record and a biometric record of a second record are from a same individual, the first record comprising a first unique identifier and the second record comprising a second unique identifier are linked. Using the first or second unique identifiers, access to information about the individual linked to both the first record in the first database and the second record in the second database is provided.

RELATED APPLICATIONS

The present application claims the benefit of priority under 35 U.S.C. §120 as a continuation of U.S. patent application Ser. No. 15/681,104,filed Aug. 18, 2017 titled “Systems and Methods for an Incremental,Reversible and Decentralized Biometric Identity Management System” whichis incorporated by reference herein in its entirety.

FIELD OF THE DISCLOSURE

The present application generally relates to scalable identitymanagement systems, including but not limited to systems and methodsthat use biometrics.

BACKGROUND

Conventionally, identity management systems use technical approachesthat are designed to optimize the final technical performance of theoverall system. However, when an identity management system is to bedeployed across countries or across different organizations, thendifferences in policy, privacy and other non-technical limitations canprevent the common deployment of those technical approaches. Moreover,once an organization has subscribed to a particular identity managementsystem and its technical approach, then it is often difficult tounsubscribe or revert back to any existing identity management system incase the new system has unforeseen drawbacks for a particularorganization, and this in itself can be a barrier to adoption. Inaddition, from a logistical viewpoint, it is perceived to be difficultand expensive to manage the deployment of an identity management systemat the same time across countries or across organizations.

BRIEF SUMMARY

In some aspects, the present disclosure is directed towards systems andmethods for a decentralized identity management system that can bedeployed incrementally one organization at a time, and also reversibly,such that any organization can unsubscribe at any time and can easilyrevert to any existing identity management system.

In one aspect, this disclosure is directed to a method for an identitymanagement system capable of being deployed incrementally. In someembodiments, the method comprises: performing, by a biometric processingengine executing on at least one server, biometric matching between afirst plurality of records from a first database and a second pluralityof records from a second database, the first database and the seconddatabase established independently of each other. Each record from thefirst and second pluralities of records may comprise a biometric record,and a corresponding identifier implemented to be unique across databasesincluding the first and second databases. The biometric processingengine may determine that a first biometric record of a first recordfrom the first database and a second biometric record of a second recordfrom the second database, are from a same individual. The first recordmay include a first unique identifier and the second record comprising asecond unique identifier. A records arbitrator may maintain in apoly-unique identity table on a storage device responsive to thedetermination, a link between the first unique identifier of the firstrecord from the first database, and the second unique identifier of thesecond record from the second database. The records arbitrator mayprovide via one or more network interfaces to the first and seconddatabases, in response to receiving a request identifying the firstunique identifier or the second unique identifier, access to informationabout the individual linked to the first record and stored in the firstdatabase, and information about the individual linked to the secondrecord and stored in the second database, according to the linkmaintained in the poly-unique identity table.

In some embodiments, determining that the first biometric record and thesecond biometric record are from the same individual comprisesdetermining that a level of matching between the first biometric recordand the second biometric record exceeds a predefined threshold. Each ofthe first biometric record and the second biometric record may includetwo types of biometric data.

In certain embodiments, the method further comprises using the firstunique identifier or the second unique identifier identified in thereceived request, to index into the poly-unique identity table toidentify the first record of the first database and the second record ofthe second database. In some embodiments, the information about theindividual linked to the first record and the information about theindividual linked to the second record comprises at least one of medicalor financial related information.

In certain embodiments, the method further comprises performingbiometric matching between a third plurality of records from a thirddatabase of the databases, and at least one of the first and secondpluralities of records, the third database established independently ofthe first and second databases. The biometric processing engine maydetermine that a third biometric record of a third record from the thirddatabase is from the same individual, the third record comprising athird unique identifier. The records arbitrator may update in thepoly-unique identity table responsive to the determination that thethird biometric record is from the same individual, the link to includethe third unique identifier of the third record from the third database.

In some embodiments, the method further comprises determining that athird biometric record of a third record from the first database is froman individual different from that corresponding to other biometricrecords in the first and second databases, the third record comprising athird unique identifier. The records arbitrator may maintain, in thepoly-unique identity table, an entry with the third unique identifier ofthe third record from the first database.

In certain embodiments, the method further comprises removing, by therecords arbitrator, from the poly-unique identity table, the linkbetween the first unique identifier of the first record from the firstdatabase and the second unique identifier of the second record from thesecond database, responsive to an instruction to cease providing accessto the information stored in the first database.

In some embodiments, the first database, the second database, and thepoly-unique identity table are each maintained by a differentorganization or entity. In certain embodiments, the first database andthe poly-unique identity table are maintained by a first organization orentity, and the second database is maintained by a second organizationor entity.

In another aspect, this disclosure is directed to a system forincremental and reversible deployment of a decentralized identitymanagement system. The system may include a biometric processing engineexecuting on at least one server. The biometric processing engine may beconfigured to perform biometric matching between a first plurality ofrecords from a first database and a second plurality of records from asecond database. The first database and the second database may beestablished independently of each other. Each record from the first andsecond pluralities of records may include a biometric record, and acorresponding identifier implemented to be unique across databasesincluding the first and second databases. The biometric processingengine may determine that a first biometric record of a first recordfrom the first database and a second biometric record of a second recordfrom the second database, are from a same individual. The first recordmay include a first unique identifier and the second record may includea second unique identifier. The system may include one or more networkinterfaces to the first and second databases. A records arbitrator maybe configured to maintain, responsive to the determination, in apoly-unique identity table on a storage device, a link between the firstunique identifier of the first record from the first database, and thesecond unique identifier of the second record from the second database.The records arbitrator may provide, via the one or more networkinterfaces, in response to receiving a request identifying the firstunique identifier or the second unique identifier, access to informationabout the individual linked to the first record and stored in the firstdatabase, and information about the individual linked to the secondrecord and stored in the second database, according to the linkmaintained in the poly-unique identity table.

In some embodiments, the biometric processing engine is furtherconfigured to determine that the first biometric record and the secondbiometric record are from the same individual, by determining that alevel of matching between the first biometric record and the secondbiometric record exceeds a predefined threshold. In some embodiments,each of the first biometric record and the second biometric recordincludes two types of biometric data.

In some embodiments, the records arbitrator is further configured to usethe first unique identifier or the second unique identifier identifiedin the received request, to index into the poly-unique identity table toidentify the first record of the first database and the second record ofthe second database. In certain embodiments, the information about theindividual linked to the first record and the information about theindividual linked to the second record comprise at least one of medicalor financial related information.

In some embodiments, the biometric processing engine is furtherconfigured to perform biometric matching between a third plurality ofrecords from a third database of the databases, and at least one of thefirst and second pluralities of records, the third database establishedindependently of the first and second databases. The biometricprocessing engine may determine that a third biometric record of a thirdrecord from the third database is from the same individual, the thirdrecord comprising a third unique identifier. The records arbitrator maybe configured to update, in the poly-unique identity table responsive tothe determination that the third biometric record is from the sameindividual, the link to include the third unique identifier of the thirdrecord from the third database.

In some embodiments, the biometric processing engine is furtherconfigured to determine that a third biometric record of a third recordfrom the first database is from an individual different from thatcorresponding to other biometric records in the first and seconddatabases, the third record comprising a third unique identifier; andthe records arbitrator is further configured to maintain, in thepoly-unique identity table, an entry with the third unique identifier ofthe third record from the first database.

In some embodiments, the records arbitrator is further configured toremove, from the poly-unique identity table, the link between the firstunique identifier of the first record from the first database and thesecond unique identifier of the second record from the second database,responsive to an instruction to cease providing access to theinformation stored in the first database.

In some embodiments, the first database, the second database, and thepoly-unique identity table are each maintained by a differentorganization or entity. In certain embodiments, the first database andthe poly-unique identity table are maintained by a first organization orentity, and the second database is maintained by a second organizationor entity.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other objects, aspects, features, and advantages ofthe present solution will become more apparent and better understood byreferring to the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram of one embodiment of a biometric identitymanagement system;

FIG. 2 illustrates poly-unique indexing in one embodiment;

FIG. 3 illustrates how accuracy of an iris biometric may depend in someembodiments on quality of the data acquisition;

FIG. 4 illustrates how accuracy of a fingerprint biometric may depend insome embodiments on quality of the data acquisition;

FIG. 5 shows an example of how one or more biometrics, and/or one ormore ancillary pieces of identifying information, may be combinedprobabilistically to make a determination of identity with a givenprobability;

FIG. 6 illustrates in one embodiment how information from a thirddatabase may be incorporated into the identity management system thatalready incorporates information from a first and second database;

FIG. 7 illustrates one embodiment of an identity management system thatmakes use of a first database in a first organization, configured toexploit the information in the first database to improve the serviceprovided to the individuals enrolled in the first database;

FIG. 8 illustrates a another embodiment of the identity managementsystem that, independently of a first database, makes use of a seconddatabase in a second organization, and is configured to exploit theinformation in the second database to improve the service provided tothe individuals enrolled in the second database;

FIG. 9 illustrates an embodiment of an identity management system thatmakes use of an independently-established first database and anindependently-established second database, and that is configured toexploit information in both the first and second databases to improveservice provided to individuals enrolled in either or both the first andsecond databases;

FIG. 10 illustrates an example embodiment of the data accesspermissioning and control module that was shown in FIG. 1, configured toenable access to Application Dataset 2 using Identifier 1;

FIG. 11 illustrates an example embodiment of the data accesspermissioning and control module that was shown in FIG. 1, configured todisable or remove access to Application Dataset 2 using Identifier 1;

FIG. 12 illustrates an example embodiment of the data accesspermissioning and control module that was shown in FIG. 1, configured todisable or remove access to Application Dataset 2 using Identifier 1,and also configured to remove the corresponding link in the poly-uniquelink table; and

FIG. 13 shows an embodiment of an implementation of the system.

DETAILED DESCRIPTION

FIG. 1 shows a block diagram of one embodiment of a system fordecentralized identity management, that is capable of being deployedincrementally. The establishment of a first database is shown at the topleft, and the independent establishment of a second database is shown atthe bottom left. In this particular embodiment, there may be threecategories of data that are either acquired, generated or retrieved inthe establishment of a database. A first category is the acquisition orretrieval of application data, which may include the name, address, dateof birth of a particular individual, and financial, medical or otherapplication-specific information that relates to the individual. Asecond category is the acquisition of a biometric dataset. This mayinclude iris biometric data, fingerprint data or any other biometricdata. This shall be discussed in more detail later in the specification.A third category is the independent generation and issuance of apoly-unique identifier. This can be contrasted to the issuance of aunique identifier, where a single individual is uniquely indexed by asingle number. FIG. 2 illustrates possible difference(s) between anon-unique, a unique and a poly-unique identifier. The first row in FIG.2 shows an example of non-unique identifiers. In this case, a givenindex does not uniquely refer to a given individual. The second row inFIG. 2 shows an example of unique identifiers. In this case, a singleindex number uniquely refers to a single individual. Database 2 may havebeen established at a later time, at a different location, or by adifferent organization compared to the establishment of Database 1,making it impossible to use a unique identifier as defined in FIG. 2since there is no coordination at the time of the establishment of thedatabases, and the generation and issuance of an index number inparticular, to avoid the potential repetition of index numbers in eachdatabase which would result in a non-unique identifier as defined inFIG. 2. The third row in FIG. 3 shows an example of poly-uniqueidentifiers. In this case more than one index number can refer to asingle individual, however the index numbers themselves are unique. Insome embodiments, the advantage of the poly-unique identifier is that anidentity management system containing biometric and other information ofone individual can be established independently without any knowledge ofa prior or future identity management system that may or may not containthe same individual. Methods for generating and issuing the poly-uniqueidentifier shall be discussed later in this specification.

Referring again to FIG. 1, as discussed previously, the ancillaryinformation, biometric information and the poly-unique identifier may insome embodiments be established completely independently of each otherand may be stored in database 1 and database 2 corresponding to identitymanagement 1 and 2 respectively, as shown. In some embodiments, afterthe identity management system(s) and the corresponding databases havebeen established independently, biometric matching may be performedbetween the biometric information stored in database 1 and the biometricinformation stored in database 2. In addition, matching of ancillarydata such as name, date of birth or address may be performed. In someembodiments the purpose of the biometric matching (with or withoutancillary data) is to determine whether the same individual is in bothdatabases. The methods for performing this matching shall be discussedin more detail later in this specification. If such a matchdetermination is made, then the poly-unique identifier from the firstidentity management system for that particular record can be associatedto the poly-unique identifier for the matched record from the secondidentity management system, and the association may be stored in thepoly-unique identity table, as shown in FIG. 2 for instance. If a matchdetermination is not made, then the poly-unique identifier from therecord may be stored in the poly-unique identity table as a separaterecord. In some embodiments, the poly-unique identity table is inputtedinto a Data Access Permissioning and Control module, as shown in FIG. 2for instance. Also inputted into the module is, in this example, thepoly-unique identifier 1 that was generated and issued and stored indatabase 1 of the first identity management system. As discussedpreviously, this poly-unique identifier may only be known to theorganization that controls and established the first identity managementsystem. In some embodiments, the data access permissioning and controlmodule then locates poly-unique identifier 1 in the poly-unique identitytable to determine whether the poly-unique identifier is associated toany other poly-unique identifiers in either identity management system 1and 2 with their corresponding databases 1 and 2 respectively. If suchan association exists, then in some embodiments the linked poly-uniqueidentifier is used to retrieve the application data for that particularrecord from either identity management system 1 or 2.

In some embodiments, this enables the Data Access Permissioning andControl module to retrieve Application Data for a particular individualfrom both identity management system 1 and 2 and their correspondingdatabases 1 and 2 respectively, using (e.g., only using) the poly-uniqueindex from the record in identity management system 1 (or from a recordin identity management system 2), even though the identity managementsystems may have been established independently by differentorganizations at different times.

As shall be described later, the method illustrated in FIG. 1 can beextended so that the Application Data for a particular individual fromany number of identity management systems that have been establishedcompletely independently at different times and by differentorganizations, can be retrieved by the Data Access Permissioning andControl module, using (e.g., only using) the poly-unique indexcorresponding to the individual known only to a single organization forinstance.

Biometric Matching

As described earlier in this specification, in some embodimentsbiometric matching is performed between biometric data from a firstidentity management system stored in a first database and biometric datafrom a second identity management system stored in a second database. Insome embodiments, the biometric matching may be performed together withthe matching of ancillary data such as name, date of birth or address.Biometrics may be used in some embodiments since ancillary informationmay be imprecise due to incorrect or ambiguous data entry, may changeover time due to name or address changes, or may be unknown with anyprecision. Biometrics have the advantage of being a function of theindividual themselves.

In some embodiments, the identity management system may be designed toeventually incorporate millions of individuals from thousands ofdecentralized identity management systems established independently. Thematch process should therefore be able to identify the same individualacross these millions of records. There are many factors however thataffect the performance of the biometric matching. A first factor is thefundamental discriminating information in a given biometric. Forexample, Daugman in U.S. Pat. No. 5,291,560 has shown that the irisbiometric can be highly discriminating, and with optimally-acquired datahas a false match rate of the order of 1 in 1 million for a single eye,and significantly higher for two eyes.

However, in one aspect of the invention, as the biometric identitymanagement system is scaled up so that millions of people are enrolled,then the inability to deploy thousands of skilled enrollment staff meansthat the quality-control of the enrollment process may decrease so thatthe data being acquired is sub-optimal. This is illustrated in moredetail in FIG. 3 for instance. The top row illustrates an optimalacquisition of iris data. The iris may be well-focused, the eye may bewide-open and the eyelashes are not occluding the iris data forinstance. In this case, the data in the iris is well-conditioned, and inthis illustrative example, 2096 bits of an iris code may be availablefor biometric matching. The bottom row may show a suboptimal acquisitionof iris data. In this case, the iris may be out-of-focus, and/or the eyemay be less open, and/or eyelashes may occlude the iris data. In thisillustrative example, there may be only 400 bits available for matching.Another example using the fingerprint biometric is shown in FIG. 4, forinstance. The top row illustrates an optimal acquisition of fingerprintdata. The fingers may be well-focused, the user may have presented theuser's fingers to a device with uniform pressure, and the fingerprintsthemselves may be clear. In this case, the data in the fingerprints maybe well-conditioned, and 20 points of interest (features such asridge-ends, for example) in each of 10 fingers can be acquired. Thebottom row illustrates sub-optimal acquisition of fingerprint data. Inthis case, the fingerprints are smudged, due to motion of the userduring the acquisition process, and the fingerprint features themselvesmay be worn, due to manual labor, for example. In this case, the data inthe fingerprints may be ill-conditioned, and there may only be 3 pointsof interest in each of the 10 fingers acquired. At the bottom of FIGS. 3and 4 are the implications, in certain embodiments, of such differencesin raw information. If both dataset 1 and dataset 2 are acquiredoptimally, then a match result with the theoretical best probability ofmatching can be recovered, as shown by the top left entry of the tableat the bottom of both FIGS. 3 and 4. However, if one or both of thedatasets contain suboptimal data, then one or more of the false-acceptrate, false-reject rate or failure-to-acquire rate can increase.

In addition, in another aspect of the invention and in certainembodiments, in addition to the fundamental information available in thebiometric data in the scaled deployment of the biometric identitymanagement system as described above, it can be useful to modify thebiometric match threshold to greatly reduce the false-reject rate or thefailure-to-acquire rate even if it means that the false-accept rate isincreased. This is because even a small failure-to-acquire rate of, forexample 0.1%, can scale to hundreds of thousands of users, and theseusers may have no biometric information assigned to them at all. Bymodifying the match threshold in this way, then almost all users canhave some biometric information assigned to them. The penalty howeverfor modifying the match threshold in this way is that the ability of theparticular biometric to differentiate between different users can begreatly reduced. This is addressed by combining multiple sources ofinformation, each with a pre-defined probability of match, in order toincrease the overall probability of match.

In more detail, FIG. 5 shows an example of such probability combinationfor various configurations of the biometric identity management system.In this example, up to 4 match probabilities are combined; 2 arebiometric match probabilities (for example from iris and fingerprintmatching respectively) with each of high and medium probability ofmatching depending on the quality of data acquisition as describedabove, and 2 are ancillary-data-based matching (e.g. name, date ofbirth, address).

The use of ancillary information such as name, date of birth, andaddress during the matching process depends in some embodiments and insome applications of the biometric identity management system on whetherthere is an incentive or disincentive for the user to purposivelyprovide incorrect information. In cases where there is no incentive topurposively provide incorrect information, then in some embodiments thenit is expected that the information provided would be partially accurate(for example, spelling mistakes or ambiguous data entry may occur) andin some embodiments it may be assumed that the match data follows aGaussian distribution. In cases where there is an incentive topurposively provide incorrect information, then the ancillaryinformation for matching can be avoided. In some embodiments, theprobabilities of match may be assumed to be independent, follow aGaussian distribution, and can be recovered from testing performed apriori. Probabilities with such properties can be combined usingstandard probability analysis such that:

P(combined)=P(1)*P(2)*P(3)* . . . /((P(1)*P(2)*P(3)* . . .)+(1−P(1))*(1−P(2))*(1−P(3))* . . . ))

where P(1), P(2), P(3) . . . are the individual probabilities of matchcontributed by each biometric or ancillary dataset.

Returning to FIG. 5, the first row shows matching performed using 1biometric (the iris in this example) wherein the data acquired isrelatively high quality. The a priori probability of an incorrect match,Pf(1), in this case is 1 in 20,000. This may appear a high probabilitycompared to the over 1 in 1 million probability of false accept reportedby Daugman in U.S. Pat. No. 5,291,560, for example, but as discussedearlier, the operating points of the biometric match algorithms in someembodiments may be adjusted in order to reduce the false-reject orfailure-to-acquire rates, at the expense of this false-accept rate.Continuing with the example in the first row in FIG. 5, no otherinformation is used in the matching for instance, such that the a prioriprobability of the other 3 factors are each 1 in 2 (50%). Theprobability of a true match, P(..) can be computed in some embodimentssuch that P(..)=1−Pf(..). Using the formula above, the combinedprobability of a true match in row 1 is then P(combined)=0.99995. In asystem that incorporates 100 million individuals, then this means that100e6×(1−0.99995)=5,000 individuals may be incorrectly matched.Depending on the application of the biometric identity managementsystem, then this error may or may not be a problem. For example, thebiometric identity management system may be designed to increase theefficiency of identity management for the vast majority of individualsin totality, even if exceptions have to be managed separately usingother processes.

Row 2 in FIG. 5 shows another example where 2 biometrics (for example,in this case, the iris and finger biometrics) are acquired and used formatching. In a system that incorporates 100 million individuals, thenalmost no individuals (0.25) are expected to be incorrectly matched. Row3 in FIG. 5 shows another example where 1 biometric is acquired, butwhere the data being acquired is sub-optimal. The a priori probabilityof false match in this example is 1 in 200. In a system that includes100 million individuals, then it is expected that 500,000 individualsmay be incorrectly matched. Row 4 in FIG. 5 shows another example where2 biometrics (iris and fingerprint) are each acquired sub-optimally andeach with an a priori probability of false match of 1 in 200. In thiscase, in a system that incorporates 100 million individuals, it isexpected that 2,525 individuals may be incorrectly matched. Row 5 inFIG. 5 shows another example where 1 biometric acquired sub-optimally isused for matching together with 2 pieces of ancillary information (e.g.name, date of birth, address), each with a 1 in 50 probability of falsematch due to misspelling and ambiguities, for example. In this case, ina system that includes 100 million individuals, then it is expected that209 individuals may be incorrectly matched. As described earlierhowever, it is important to understand whether the matchingcharacteristics of the ancillary data follows a Gaussian distribution orwhether the distribution is skewed by an incentive or disincentive forthe user to provide incorrect information. Row 6 in FIG. 5 shows theresult of matching using 2 biometrics acquired sub-optimally, and 2pieces of ancillary information. In this case, in a system thatincorporates 100 million individuals, then it is expected that 1 (1.05)individuals may be incorrectly matched.

Poly-Unique Index Generation

As described earlier in this specification, in some embodiments, theadvantage of the poly-unique identifier is that an identity managementsystem that includes or maintains biometric and other information forone individual can be established independently without any knowledge ofa prior or future identity management systems that may or may notcontain the same individual.

In some different biometric identity management systems, index numberscomprising 11 digits for instance, have been used. Even though this 11digit number can index over 99 billion (99×10{circumflex over ( )}9)users in a coordinated fashion, if these index numbers are generated andissued independently as in an embodiment of this invention, then theprobability of two indices being the same is remarkably high even aftera relatively small number of indices have been independently issued. Inmore detail, from probability analysis, the probability P of oneinstance of two independently-generated numbers being the same, forlarge numbers, is:

P=1−e{circumflex over ( )}((−n(n−1)/2)/q)

where q is the number of possible indices in the range, and n is thenumber of users to whom index numbers have been generated and assignedindependently. In the case of an 11 digit index number, thenq=99,999,999,999 at most. For an approximately P=50% probability of 2independently-generated numbers being the same, the number of users towhom index numbers have been assigned independently would be justn=375,000. For an approximately P=95% probability of 2 independentlyassigned numbers being the same, then n=780,000. For a biometricidentity management system that is to be deployed to incorporatemillions of individuals, this is unacceptable since there is anextremely high probability that an index number for an individual can benon-unique, as shown in the first row of FIG. 2.

In one embodiment, the poly-unique index is generated such that theprobability of re-occurrence of the independently-generated indices issmall, and in some embodiments this probability of re-occurrence may beless than the probability of an incorrect match from the biometric matchengine to ensure that the performance of the indexing method is able tomeet or exceed the performance of the matching process to ensure precisecorrespondence of records.

In some embodiments, the poly-unique index is generated using aUniversally-Unique-Identifier (UUID) algorithm, such as that proposed bySun Microsystems.

In certain embodiments, the result is a 128 bit number where 103trillion independently-generated indices are to be generated beforethere is a 1 in 1 billion probability of a duplication.

Incremental Updating of the Decentralized Biometric Identity ManagementSystem

As mentioned earlier, in one aspect of the embodiment, the methodillustrated in FIG. 1 can be extended so that the Application Data for aparticular individual from any number of identity management systemsthat have been established independently at different times and bydifferent organizations, can be retrieved by the Data AccessPermissioning and Control module, using just the poly-unique indexcorresponding to the individual known only to a single organization forinstance. FIG. 6 shows a specific example of one embodiment of thisupdating process. In this case it is assumed that the poly-unique linktable already exists corresponding to the first identity managementsystem and its corresponding database and the second identity managementsystem and its corresponding database using the methods describedpreviously. In FIG. 6, a third independently-established identitymanagement system and its corresponding database is then incorporatedincrementally into the biometric identity management system in the sameway that the second and first databases were incorporated. Specifically,biometric matching is performed between the biometric data in theindependently-established first and second identity management systems,and the biometric data in the independently-established andincrementally-introduced third identity management system, as shown inFIG. 6. If a determination of a match is made, then the poly-uniqueidentifier from the third identity management system and for thatparticular record can be associated to the poly-unique identifier forthe matched record from the first and/or second identity managementsystem, and the poly-unique identity table may be updated and theassociation stored, as shown in FIG. 6 for instance. If a determinationof a match is not made, then the poly-unique identity table may beupdated such that the identifier from the record is stored as a separaterecord. In some embodiments, the poly-unique identity table is inputtedinto a Data Access Permissioning and Control module, as shown in FIG. 6.Also inputted into the module is, in this example, the poly-uniqueidentifier 1 that was generated and issued and stored in the firstidentity management system and its corresponding database. As discussedpreviously, this poly-unique identifier may only be known to theorganization that controls and established the first identity managementsystem. In some embodiments, the data access permissioning and controlmodule then locates poly-unique identifier 1 in the poly-unique identitytable to determine whether the poly-unique identifier is associated toany other poly-unique identifiers in either identity management systems1, 2 or 3. If such an association exists, then in some embodiments thelinked poly-unique identifier is used to retrieve the application datafor that particular record from either identity management system 1, 2or 3.

In some embodiments, this enables the Data Access Permissioning andControl module to retrieve Application Data for a particular individualfrom identity management systems 1,2 and 3, using (e.g., only using) thesingle poly-unique index from a record in identity management system 1(or from a record in identity management system 2 or 3), even though theidentity management systems may have been established independently bydifferent organizations at different times. This shows how in someembodiments the decentralized biometric identity management system canbe deployed incrementally across countries or across differentorganizations at different times.

Example Use Case of Incremental and Decentralized Deployment

FIG. 7 illustrates one example embodiment of a decentralized biometricidentity management system. The decentralized biometric identitymanagement system may make use of a first database in a firstorganization, and may be configured to exploit the information in afirst database corresponding to a first identity management system toimprove the service provided to the individuals enrolled in the firstdatabase. More specifically, as indicated in FIG. 7, the improvedservice may in some embodiments include reliable access to theindividual's information (as opposed to the retrieval of anotherindividual's information), and data mining that makes use of theindividual's information tracked reliably over time or across differentorganizations. FIG. 8 illustrates another instantiation of the samebiometric identity management system established independently foranother set of individuals. Similarly, the embodiment in FIG. 8 may alsobe configured to exploit the information in the database to improve theservice provided to the individuals enrolled in the database. Note thattwo (2) of the individuals are in common between the instantiation ofthe biometric identity management system in FIG. 7 and the instantiationin FIG. 8. For example, the biometric identity management systems inFIGS. 7 and 8 may have been established independently by two differentorganizations, and the individual may subscribe to, or be in ahealthcare program by, both organizations. FIG. 9 shows how in someembodiments the decentralized biometric identity management systemincrementally makes use of the information established independently inthe separate system instantiations shown in FIGS. 7 and 8, such that theservice provided to the individuals in the system instantiation in FIG.9 incorporates information individually or in aggregate from bothidentity management systems. In some embodiments, this may significantlyimprove the service or level of care provided to the individual.

Privacy

In some embodiments, as information is aggregated from multipledatabases then privacy of the information exchanged may become an issue.For example, repeated requests made to an individual's record in adatabase that pertains to a particular topic (such as a disease) exposesa relationship between the individual and that topic even though thecontent of the information is unknown. In some embodiments, this problemcan be solved using two methods. The first method is the use ofobfuscation. In this method, many false exchanges or queries are made toa database in order to obscure the real information exchange betweensystems. If the number of false exchanges exceeds the number of trueexchanges by a factor of 100, for example, then it is difficult forautomatic algorithms to determine which exchanges contain realinformation. The second method is the use of zero-knowledge proofs. Inthis method, a query can be made from one system to the next and anaffirmative or negative response provided, without revealing anyinformation in the query. The method can be implemented usingcryptographic methods that are, for example, described in detail in“Zero-Knowledge Proof and Authentication Protocols” by Benjamin Lipton.

Removing Access to Data

In some embodiments of biometric identity management systems, theissuance and use of a centralized index number is a potential barrier toadoption since once such an index number has been issued for anindividual, it may be difficult to revoke it and unsubscribe from itsuse. In some cases, organizations may be more comfortable providingaccess to their data as long as they can easily remove access seamlesslyat a later time and continue exploiting the data themselvesindependently. Methods for performing this, in some embodiments, areshown in FIGS. 10,11 and 12. FIGS. 10, 11 and 12 show an expandedversion of a Data Access Permissioning and Control module, for examplethe Data Access Permissioning and Control module that was shown in FIGS.1 and 6. The Data Access Permissioning and Control module includes twocomponents: a Permissioning Decision module and a Data Access Controlmodule. The Permissioning Decision module has one or more PermissionPolicy Decisions as input. In some embodiments, these decisions may beconfigured to be one or more signals or data fields. In someembodiments, a particular signal or data-field controlling access to agiven identity management system and its corresponding database may becontrolled solely by the organization controlling the given identitymanagement system. In some embodiments, the signal or data-field canthen be used in one or both of two ways. In one embodiment, the signalor data-field is used to control the Data Access Control module so thatother organizations cannot access the data in the given identitymanagement system and its corresponding database leaving access to otherdatabases intact. This disabling of access is for example shown in FIG.11 where the Permissioning Decision module provides a control signal tothe Data Access Control module that prevents access to the data in thegiven identity management system and its corresponding database. In someembodiments of the system shown in FIG. 11, access to the given identitymanagement system and its corresponding database can be re-enabled ifthe organization controlling the given database provides the appropriatesignal or data-field input into the Permissioning Decision Module. Thiscan be contrasted to the method shown in FIG. 12 whereby a signal fromthe Permissioning Decision module is used to remove all links for allpoly-unique indices from the given identity management system stored inthe poly-unique link table. This irreversibly removes any associationbetween the data held by the given organization and all otherorganizations and their corresponding identity management systems. Ifthe given organization also prevents other organizations from accessingthe biometric data sets in its identity management system and itscorresponding database, then the poly-unique link table cannot berecreated to include the given identity management system. The givenorganization however can continue to use the poly-unique indices that itgenerated independently for its own instantiation of the biometricidentity management system, and can at a later time re-subscribe to thelarger biometric identity management system that incorporates otherbiometric identity management systems from other organizations.

FIG. 13 shows an implementation of the system. At the top left is afirst processor, which in some embodiments may comprise a Dell Inspiron3650 computer with an integrated network interface for instance. Amonitor and mouse are connected to the computer. Connected to theprocessor by network or USB link are two biometric devices; an iris dataacquisition device and a fingerprint data acquisition device. In someembodiments, these devices may comprise a CIS 202 iris readermanufactured by 3M, and a Morphotop 100 fingerprint reader devicemanufactured by Safran, as examples. At the bottom left is anindependently-established system that in some embodiments may comprisesimilar or the same components. Internal to each computer is a storagedevice, as shown in FIG. 13.

A biometrics matching server, that in some embodiments may also comprisea Dell Inspiron 3650 computer with an integrated network interface forexample, is connected to the first and second processor by computernetwork via the network interfaces. Internal to the computer is astorage unit which is connected by a network interface to the processor,as shown in FIG. 13. Connected to the biometric matching server and itsstorage module is a Data Access Permissioning and Control server thatmay also comprise in some embodiments a Dell Inspiron 3650 computer forinstance. A client processor that in some embodiments may also comprisea Dell Inspiron 3650 computer for instance, is connected via a networkinterface to the Data Access Permissioning and Control server, which inturn may also be connected via network interfaces to theindependently-generated databases in Storage Unit 1 and 2 respectively.

In this particular embodiment, ancillary data and biometric data forindividuals may be acquired using the biometric devices and thecomputers shown at the top left and bottom left of FIG. 13. In someembodiments, the poly-unique index generation may be performed on thisprocessor. Again in this particular embodiment, the biometric data maybe sent via network interface to the biometrics matching server wherebiometric match algorithms are performed. In some embodiments, thesematch algorithms may comprise the Fingerprint SDK and Iris RecognitionSDK supplied by Neurotechnology for instance. The poly-unique link tablemay in some embodiments may be generated by the biometric match serverand stored on the connected storage unit.

An application connected to a client computer (shown at the top right ofFIG. 13) may in some embodiments make a request for Application Datasetinformation for an individual using poly-unique identifier 1. Therequest may be sent via network interface to the Data Access Permissionand Control server, which accesses the poly-unique link table andaccesses any permission flags or signals. In this particular embodiment,the Data Access Permission and Control server then accesses Storage unit1 and 2 respectively, retrieves Application Dataset 1 and 2, andre-transmits it via network interface to the client computer as shown.

Each of the elements, modules, submodules or entities, referenced hereinin connection with any embodiment of the present systems or devices, isimplemented in hardware, or a combination of hardware and software. Forinstance, each of these elements, modules, submodules or entities caninclude any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of the respective system. The hardware includes circuitry suchas one or more processors, for example.

It should be understood that the systems described above may providemultiple ones of any or each of those components and these componentsmay be provided on either a standalone machine or, in some embodiments,on multiple machines in a distributed system. The systems and methodsdescribed above may be implemented as a method, apparatus or article ofmanufacture using programming and/or engineering techniques to producesoftware, firmware, hardware, or any combination thereof. In addition,the systems and methods described above may be provided as one or morecomputer-readable programs embodied on or in one or more articles ofmanufacture. The term “article of manufacture” as used herein isintended to encompass code or logic accessible from and embedded in oneor more computer-readable devices, firmware, programmable logic, memorydevices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g.,integrated circuit chip, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), etc.), electronicdevices, a computer readable non-volatile storage unit (e.g., CD-ROM,floppy disk, hard disk drive, etc.). The article of manufacture may beaccessible from a file server providing access to the computer-readableprograms via a network transmission line, wireless transmission media,signals propagating through space, radio waves, infrared signals, etc.The article of manufacture may be a flash memory card or a magnetictape. The article of manufacture includes hardware logic as well assoftware or programmable code embedded in a computer readable mediumthat is executed by a processor. In general, the computer-readableprograms may be implemented in any programming language, such as LISP,PERL, C, C++, C#, PROLOG, or in any byte code language such as JAVA. Thesoftware programs may be stored on or in one or more articles ofmanufacture as object code.

While various embodiments of the methods and systems have beendescribed, these embodiments are exemplary and in no way limit the scopeof the described methods or systems. Those having skill in the relevantart can effect changes to form and details of the described methods andsystems without departing from the broadest scope of the describedmethods and systems. Thus, the scope of the methods and systemsdescribed herein should not be limited by any of the exemplaryembodiments and should be defined in accordance with the accompanyingclaims and their equivalents.

We claim:
 1. A method for an identity management system capable of beingdeployed incrementally, comprising: performing, by a biometricprocessing engine executing on at least one server, biometric matchingbetween a first plurality of records from a first database and a secondplurality of records from a second database, the first database and thesecond database comprising financial-related or criminal-relateddatabases established independently of each other, wherein each recordfrom the first and second pluralities of records comprises a biometricrecord, and a corresponding identifier implemented to be unique acrossdatabases including the first and second databases; determining, by thebiometric processing engine, that a first biometric record of a firstrecord from the first database and a second biometric record of a secondrecord from the second database, are from a same individual, the firstrecord comprising a first unique identifier and the second recordcomprising a second unique identifier; maintaining, by a recordsarbitrator, in a poly-unique identity table on a storage deviceresponsive to the determination, a link between the first uniqueidentifier of the first record from the first database, and the secondunique identifier of the second record from the second database; andproviding, by the records arbitrator via one or more network interfacesto the first and second databases, in response to receiving a requestidentifying the first unique identifier or the second unique identifier,access to information about the individual linked to or stored with thefirst record of the first database, and information about the individuallinked to or stored with the second record of the second database,according to the link maintained in the poly-unique identity table. 2.The method of claim 1, wherein determining that the first biometricrecord and the second biometric record are from the same individualcomprises determining that a level of matching between the firstbiometric record and the second biometric record exceeds a predefinedthreshold.
 3. The method of claim 1, wherein each of the first biometricrecord and the second biometric record includes two types of biometricdata.
 4. The method of claim 1, further comprising using the firstunique identifier or the second unique identifier identified in thereceived request, to index into the poly-unique identity table toidentify the first record of the first database and the second record ofthe second database.
 5. The method of claim 1, wherein the informationabout the individual linked to the first record and the informationabout the individual linked to the second record comprise at least oneof medical, criminal or credit-score related information.
 6. The methodof claim 1, further comprising: performing biometric matching between athird plurality of records from a third database of the databases, andat least one of the first and second pluralities of records, the thirddatabase established independently of the first and second databases;determining that a third biometric record of a third record from thethird database is from the same individual, the third record comprisinga third unique identifier; and updating, by the records arbitrator, inthe poly-unique identity table responsive to the determination that thethird biometric record is from the same individual, the link to includethe third unique identifier of the third record from the third database.7. The method of claim 1, further comprising: determining that a thirdbiometric record of a third record from the first database is from anindividual different from that corresponding to other biometric recordsin the first and second databases, the third record comprising a thirdunique identifier; and maintaining, by the records arbitrator, in thepoly-unique identity table, an entry with the third unique identifier ofthe third record from the first database.
 8. The method of claim 1,further comprising removing, by the records arbitrator, from thepoly-unique identity table, the link between the first unique identifierof the first record from the first database and the second uniqueidentifier of the second record from the second database, responsive toan instruction to cease providing access to the information stored inthe first database.
 9. The method of claim 1, wherein the firstdatabase, the second database, and the poly-unique identity table areeach maintained by a different organization or entity.
 10. The method ofclaim 1, wherein the first database and the poly-unique identity tableare maintained by a first organization or entity, and the seconddatabase is maintained by a second organization or entity.
 11. A systemfor decentralized identity management, that is capable of being deployedincrementally, the system comprising: a biometric processing engineexecuting on at least one server, the biometric processing engineconfigured to: perform biometric matching between a first plurality ofrecords from a first database and a second plurality of records from asecond database, the first database and the second database comprisingfinancial-related or criminal-related databases establishedindependently of each other, wherein each record from the first andsecond pluralities of records comprises a biometric record, and acorresponding identifier implemented to be unique across databasesincluding the first and second databases; determine that a firstbiometric record of a first record from the first database and a secondbiometric record of a second record from the second database, are from asame individual, the first record comprising a first unique identifierand the second record comprising a second unique identifier; one or morenetwork interfaces to the first and second databases; and a recordsarbitrator configured to: maintain, responsive to the determination, ina poly-unique identity table on a storage device, a link between thefirst unique identifier of the first record from the first database, andthe second unique identifier of the second record from the seconddatabase; and provide, via the one or more network interfaces, inresponse to receiving a request identifying the first unique identifieror the second unique identifier, access to information about theindividual linked to or stored with the first record of the firstdatabase, and information about the individual linked to or stored withthe second record of the second database, according to the linkmaintained in the poly-unique identity table.
 12. The system of claim11, wherein the biometric processing engine is further configured todetermine that the first biometric record and the second biometricrecord are from the same individual, by determining that a level ofmatching between the first biometric record and the second biometricrecord exceeds a predefined threshold.
 13. The system of claim 11,wherein each of the first biometric record and the second biometricrecord includes two types of biometric data.
 14. The system of claim 11,wherein the records arbitrator is further configured to use the firstunique identifier or the second unique identifier identified in thereceived request, to index into the poly-unique identity table toidentify the first record of the first database and the second record ofthe second database.
 15. The system of claim 11, wherein the informationabout the individual linked to the first record and the informationabout the individual linked to the second record comprise at least oneof medical, criminal or credit-score related information.
 16. The systemof claim 11, wherein the biometric processing engine is furtherconfigured to: perform biometric matching between a third plurality ofrecords from a third database of the databases, and at least one of thefirst and second pluralities of records, the third database establishedindependently of the first and second databases; and determine that athird biometric record of a third record from the third database is fromthe same individual, the third record comprising a third uniqueidentifier; and the records arbitrator is further configured to update,in the poly-unique identity table responsive to the determination thatthe third biometric record is from the same individual, the link toinclude the third unique identifier of the third record from the thirddatabase.
 17. The system of claim 11, wherein the biometric processingengine is further configured to determine that a third biometric recordof a third record from the first database is from an individualdifferent from that corresponding to other biometric records in thefirst and second databases, the third record comprising a third uniqueidentifier; and the records arbitrator is further configured tomaintain, in the poly-unique identity table, an entry with the thirdunique identifier of the third record from the first database.
 18. Thesystem of claim 11, wherein the records arbitrator is further configuredto remove, from the poly-unique identity table, the link between thefirst unique identifier of the first record from the first database andthe second unique identifier of the second record from the seconddatabase, responsive to an instruction to cease providing access to theinformation stored in the first database.
 19. The system of claim 11,wherein the first database, the second database, and the poly-uniqueidentity table are each maintained by a different organization orentity.
 20. The system of claim 11, wherein the first database and thepoly-unique identity table are maintained by a first organization orentity, and the second database is maintained by a second organizationor entity.